Repository navigation
chore(deps): Update dependency semgrep to v1.179.0 - #170
Merged
Merged
Conversation
|
Important Review skippedBot user detected. To trigger a single review, invoke the ⚙️ Run configuration
You can disable this status message by setting the Use the checkbox below for a quick retry:
Comment |
Contributor
Author
Edited/Blocked NotificationRenovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR. You can manually request rebase by checking the rebase/retry box above. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
1.174.0→1.179.0Release Notes
semgrep/semgrep (semgrep)
v1.179.0Compare Source
1.179.0 - 2026-10-01
### Added
bun.locklockfiles (text format,lockfileVersion1) paired with apackage.jsonmanifest, including the dependency relationships between packages. The deprecated binarybun.lockbformat is still unsupported. (SC-2419)### Changed
Pro: Stabilize file processing order in inter-file analysis, which was previously arbitrary but deterministic. We believe this is very unlikely to affect findings but there is a theoretical path by which it could in certain rare cases. (stabilize)
c grammar update (v0.24.2):
(c-v0.24.2)
cpp grammar update (v0.23.4):
(cpp-v0.23.4)
Update the html grammar to v0.23.2. (html-v0.23.2)
r grammar update (v1.3.0):
(r-v1.3.0)
sfapex grammar update (v2.3):
(sfapex-v2.3)
### Fixed
except A, B:andexcept A, B, C:(PEP 758, Python 3.14) and theexcept*forms of both are now parsed as a tuple of exception types, likeexcept (A, B):, rather than as the Python 2except A as B:or a parseerror.
except*is now handled by Semgrep's primary Python parser too, soexception groups no longer depend on the fallback parser. Note that Python
2's
except A, e:is no longer read asexcept A as e:, even forpython2.One limitation remains: the vendored tree-sitter Python grammar still accepts
only a single comma, so
except A, B, C:is still a parse error there. Themenhir parser runs first and handles it, so this only surfaces if the
tree-sitter fallback is reached; upgrading the vendored grammar is follow-up
work. (gh-11906)
EXPOSEports with TCP/UDP protocols. (gh-11934)pyjwt[crypto]>=2.15.0,<3) instead ofpinning
~=2.13.0, so installs pick up a PyJWT release with fixes for knownvulnerabilities, and projects that require a newer PyJWT can install Semgrep. (gh-11953)
v1.178.0Compare Source
1.178.0 - 2026-09-23
### Changed
### Fixed
semgrep-coreexited on Windows. (windows-hang)v1.177.01.177.0 - 2026-09-10
### Added
rules_jvm_external. Semgrep now recognizes amaven_install.jsonpinned lockfile (versions0.1.0and3, as emitted by rules_jvm_external 3.x through current) paired with aMODULE.bazel(or legacyWORKSPACE/WORKSPACE.bazel) marker as a Maven-ecosystem subproject, and attributes findings to the workspace root rather than the lockfile's directory. Workspace-declared root artifacts are identified via__INPUT_ARTIFACTS_HASHfor accurate direct-vs-transitive classification; dependencies are emitted withUnknowntransitivity when that field is not available. This is the first milestone of native Bazel coverage; broader ecosystem support (rules_python,rules_go,rules_js) and Bazel-aware reachability attribution follow. (SC-2008)regex are inefficient to run on our default regex engine (currently PCRE2). For
example, a rule matching
FOOBAR(a+)\1will skip any file that does notcontain
FOOBARwithout running the regex. (scrt-979)### Changed
expensive regex predicates. Since evaluation short-circuits, a file that a
string check already rules in or out no longer pays for regex predicates
(which is what a pattern's prefilter falls back to when no literal substring
can be extracted from it, and which can be slow on files with very long
lines). (prefilter-rank-conjuncts)
--x-gradle-module-attribution. Enabling it can change finding IDs because finding paths change; the ID calculation is unchanged. (SC-2560)### Fixed
Speed up
semgrep cifiltering when a deployment has many triage-ignored findings. (triage-ignored-performance)Semgrep no longer crashes with an OCaml stack trace when a proxy environment
variable holds an unusable value.
HTTP_PROXY,HTTPS_PROXY, orALL_PROXYset to an empty value is now ignored with a warning, and the scan
proceeds without a proxy. A non-empty value that is not a usable proxy URL
now exits with an error message, with any credentials in the URL
redacted, instead of failing inside the HTTP client.
Semgrep also now adds the missing scheme to a proxy URL supplied
without one;
httpsforHTTPS_PROXY andhttp` otherwise. (ENGINE-2208)Supply Chain: lockfileless Gradle scans now report a "Resource Inaccessible"
resolution error when a repository refuses a request (for example a 401 from a
private registry), instead of exiting successfully with a silently incomplete
dependency list. (sc-3358)
### Infra/Release Changes
v1.176.0### Changed
v1.175.1### Fixed
--tracethat would fail withStdlib.Effect.Unhandled(Eio__core__Cancel.Get_context)when a secret would fail to validate (CODE-9906)v1.175.0Compare Source
1.175.0 - 2026-08-26
### Changed
### Known Issues
Configuration
📅 Schedule: (in timezone Europe/Berlin)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.